ABC DPT Module — Testing Playbook

Manage Settings Workflow

Manage Settings is the control center. It's expanded by default and displays the verification date range, real-time statistics, memos, and reset functionality. This is where every verification cycle begins.

• Set Verification Date Range — Enter "From" (inclusive at 12:01 a.m.) and "To" dates (inclusive at 11:59:59 p.m.). These dates control when the portal checkbox is visible to member users. Dates in the past are permitted; the To date is also known as the "Through Date."
• Monitor Progress — View the count of companies that have verified (numerator) and total companies (denominator), plus a percentage. This refreshes as verification happens in real time.
• Manage Memos — Three memo fields appear: Portal Instructions (shown in the portal to users), Email Proof (sent to companies via email when verification is requested), and Printed Proof (included in printed outputs). Each can be rich text.
• Reset All Flags — A button clears ALL verification flags across all companies. This is destructive; no historical data is retained. Use with caution when cycling from one verification period to the next.

Filter & View Companies Workflow

Filtering narrows the dataset; viewing applies actions. Together they enable targeted verification management across large company rosters.

• Apply Filters — Use dropdowns and text fields to filter by member type, company type, region, paid dues year, specific dates, STEP year, company name keyword, and current verification status (verified vs. unverified).
• View Results — Filtered companies appear in a table with checkboxes in the leftmost column. Each row shows company name, member type, region, and verification status indicator.
• Bulk Mark as Verified — Check one or more company rows, then click "Mark as Verified." This sets the verification flag, records the current date and logged-in user, and triggers any configured memo notifications.
• Inline Verification — Click an individual company to open its detail view, where you can verify it directly without using bulk checkboxes.

Fields to Include in Outputs Workflow

This section determines what data appears in reports and emails. It includes preference set management for reusable field configurations.

• Trade Code Options — Radio buttons (mutually exclusive) to select CSI, NAICS, or Directory Codes as the primary trade classification in outputs.
• Trade Code Limitations — When CSI is selected, radio buttons appear for "CSI Division" and "CSI Subdivision" filtering. These are grayed out if CSI option is unchecked.
• Demographics & Proof Fields — Checkboxes for business license, designations, volume data, contact counts, proof fields (e.g., "Check here if no changes"), and more.
• Preference Sets — Save the current field selections as a named Preference Set, then load and reuse them across multiple output sessions. Preference sets do NOT persist across browser sessions; they're stored locally only.

Email Generation Workflow

Sending verification emails is a high-stakes operation. The workflow includes preview/rehearsal, strong warnings, and confirmation steps.

• Compose Email — Select a company or group of companies, choose which contact types to send to (default: primary contact if none selected), insert the Email Proof memo, and draft the message body.
• Preview & Rehearsal — Before sending, preview emails to confirm content, recipient, subject line, and attachments. A warning appears if this step is skipped.
• Confirmation Prompt — A modal confirms you're about to send to N contacts. If you proceed, emails are queued for delivery.
• Send — Emails are sent immediately or queued based on system settings. Sent records are logged with timestamp and user.

Report Generation Workflow (12 Report Types)

DPT supports 12 distinct report formats grouped by purpose:

• Directory Reports — Excel Single, Excel Multiple, and Printed 3-column. These show all verified companies formatted for the chapter directory.
• Trades by Division — Excel, Printed 3-column, and Simple List. These group companies by CSI Division or NAICS category.
• Trades by Detail — Excel, Printed 3-column, and Simple List. These break down by CSI Subdivision or NAICS subclass for deeper segmentation.
• Proof Reports — Excel Single, Excel Contact Types, and Printed. These list companies that have verified and include proof field (e.g., "Check here if no changes").

QA must test each report type to confirm correct data inclusion, proper formatting, and field visibility based on the Fields to Include in Outputs selections.

Portal Verification (Member-Side)

During an active verification date range, member portal users see a verification checkbox and the Portal Instructions memo. When they check the box and submit:

• The company's verification flag is set to TRUE
• The current date and user ID are recorded
• The checkbox becomes unavailable after the To date passes
• Staff can view the recorded verification date/user in the View Companies section

Core Testing Pillars

DPT testing spans six core domains. Each requires distinct test cases and validation approaches:

• Manage Settings Validation — Test date range entry (past, present, future), From/To date inclusivity (12:01 a.m. to 11:59:59 p.m.), memo entry and display, real-time verified count updates, and reset flag behavior (ensure all flags clear, no data remains).
• Filter Accuracy — Verify each filter (member type, company type, region, dues year, dates, STEP year, name keyword, verification status) returns correct company subsets. Test filter combinations and edge cases (no results, all results).
• View Companies & Bulk Actions — Test checkbox selection, bulk "Mark as Verified" functionality, inline verification, and confirmation prompts. Validate that verification date and user are recorded correctly.
• Trade Code Interactions — Test CSI selection/unchecking (Division and Subdivision radio buttons enable/disable correctly), NAICS selection, Directory Code selection, and mutual exclusivity of trade code options.
• Report Generation (12 Types) — Generate each of the 12 report types and validate correct data inclusion, field visibility based on Fields to Include selections, formatting (Excel columns, printed 3-column layout), and correct trade code grouping.
• Email Workflows — Test email composition, preview/rehearsal mode, skip-preview warning, confirmation prompt, successful send, recipient validation (contact type selection), memo inclusion, and delivery logging.

Portal Integration Testing

The member portal must correctly display and handle verification during active date ranges. Test scenarios:

• Verification checkbox appears when current date/time falls within the From/To range
• Portal Memo displays correctly above or adjacent to the checkbox
• Checking the box and submitting sets the verification flag and records date/user
• Checkbox becomes unavailable immediately after the To date passes at 11:59:59 p.m.
• Portal users see their verification status correctly reflected (verified vs. unverified state)

Permission Enforcement

DPT is strictly Level 3 Chapter User access only. Test that:

• Non-Level-3 users cannot access DPT (receive permission denied message)
• Level 3 Chapter Users from other chapters cannot access another chapter's DPT instance
• Level 3 Chapter Users in the correct chapter can fully access all sections

Data Integrity & State Testing

Test that DPT correctly maintains state across actions:

• Verification flags persist correctly after setting and page refresh
• Memo text is saved and retrieved without corruption
• Preference sets are created, saved, and loaded within a session
• Fields to Include selections carry over correctly when generating multiple reports
• Bulk verification marks all selected companies (test with 1, 10, 100+ companies)
• Reset clears all flags and does not affect other data (company names, contact info remain intact)

Creative QA Scenarios to Test Edge Cases

These scenarios push DPT into corner cases that may reveal bugs or unexpected behavior. Build test cases around each:

Prerequisites for DPT Testing

To conduct comprehensive DPT testing, your test environment must be seeded with realistic data. Follow these setup instructions:

Test Data Requirements

• Companies with Trade Codes — Create or use existing companies with CSI codes (Division and Subdivision levels), NAICS codes, and Directory Codes. Test data should include companies with all three code types so you can test trade code filtering and reporting.
• Diverse Company Types — Include companies of different types (general contractor, subcontractor, supplier, vendor, etc.) to test filtering by company type and ensure reports correctly segment by type.
• Geographic Spread — Create companies in multiple regions/chapters so you can test regional filtering and multi-region reports.
• Member Types — Include companies with different member types (regular, associate, supplier, etc.) to validate member type filtering.
• Varying Dues Status — Some companies should have paid dues for multiple years, some for current year only, some with gaps, to test dues-year filtering.
• STEP Programs — Include companies enrolled in different STEP years to test STEP year filtering.
• Designations — Some companies should have multiple designations (e.g., certified contractor, sustainability program member) so you can test designation fields in outputs.
• Do Not Print Flags — Create at least 2–3 companies with "Do Not Print in Directory" flag and 2–3 with "Do Not Print Volume" flag to test exclusion logic.
• Portal Users — Ensure test companies have associated portal user accounts so you can test portal verification workflows.

Environment Configuration

• Active Verification Date Range — Set a verification date range in your test environment that includes today's date. For example, if testing on 2026-04-07, set From: 2026-04-01, To: 2026-06-30. This enables portal verification testing without manipulating system time.
• Memo Content — Populate all three memo fields in Manage Settings with sample text: Portal Instructions (e.g., "Please verify your company information..."), Email Proof (e.g., "You have 30 days to respond..."), and Printed Proof (e.g., "Submit this form if no changes required...").
• User Accounts — Create at least one Level 3 Chapter Staff test account so you can test DPT access and permission enforcement. Also create non-Level-3 accounts to test permission denial.
• Time Zone Alignment — Ensure the test system's time zone is known and consistent. Date range validation (12:01 a.m. to 11:59:59 p.m.) depends on correct time zone interpretation.

Test Cycles and Snapshot Restoration

• Snapshot Before Cycle — Before starting a full DPT testing cycle, create a database snapshot so you can restore it and re-run tests without accumulating data pollution.
• Reset for Fresh Cycle — After completing a full test pass, reset all verification flags using the "Reset All Flags" button (this clears the cycle for the next test) or restore from snapshot.
• Separate Report Testing — Generate reports in a safe test environment. Don't overwrite production report templates or outputs during testing.

Mocking & Integration Considerations

• Email Delivery — Ensure test emails are captured by a test email service or sandbox mailbox, not sent to real addresses. Verify subject, body, memo inclusion, and recipient fields without sending spam.
• Report Outputs — Excel and PDF generation should use test file storage (not production cloud storage). Verify file format, data accuracy, and formatting without polluting production archives.
• Portal Rendering — Test portal verification in a staging environment, not production, to avoid confusing real members. Use test portal user accounts with test company data.